Progress LoadMaster End of Life (EOL) Dates & Support Timeline

Progress LoadMaster lifecycle status — the real story

Progress LoadMaster (Kemp LoadMaster until Progress bought Kemp in 2021) is an application delivery controller sold as hardware appliances (LM-X and LM-XHC series, with earlier LM-2000 to LM-8020 generations and the LMB bare-metal images) and as virtual appliances (VLM), all running the LoadMaster Operating System (LMOS). Kemp's End of Life (EOL) Product Lifecycle Support Policy is the only lifecycle page: it prints an End-of-Sale month and a current equivalent model for every retired appliance, and states that "Kemp Technologies will provide Hardware/Platform Maintenance and Operating System Software service and support for 5 years from the End-of-Sale date", during which "Kemp will provide bug fixes, maintenance releases, workarounds, or patches for critical bugs reported". It prints no end-of-life column.

The end-of-life days that are served come from Progress's LoadMaster release notes, which name retired models with a day: "as of February 1, 2025, the following models have reached their end of life (EOL) and are no longer supported: LMB-1G LMB-2G LMB-5G LMB-10G LM-8000 LM-8010-MT LM-8020 VLM-200 VLM-5000 VLM-10G" (all End-of-Sale February 2020). Older models that the release notes list as unsupported are served as ended without a day; models still listed as supported for upgrade (LM-3000, LM-3400, LM-4000, LM-5600, LM-8020M, VLM-2000, LMB-MAX) are served as not ended even where the five-year window has passed, because the vendor's printed status wins over a computed policy date. The LM-X3, LM-X15, LM-X25, LM-X40 and LM-XHC appliances went End-of-Sale in 2023 and 2024 and remain supported; the bare-metal LoadMaster went End-of-Sale on January 3, 2025.

LMOS ships on three branches, GA (7.2.63.x), Long Term Support Feature (LTSF, 7.2.54.x) and the older LTS (7.2.48.x); Progress prints release days but no end-of-support date for any branch, so the three branch rows carry the latest build and no end date. CISA's Known Exploited Vulnerabilities catalog lists two LoadMaster entries, CVE-2024-1212 (OS command injection, added November 18, 2024) and CVE-2026-8037 (command injection, added August 7, 2026), neither flagged as used in ransomware campaigns (catalog 2026.10.08). Field mapping: endOfSale is the first day of Kemp's End-of-Sale month; eol is the release-notes day where printed, otherwise a boolean; successor is Kemp's "Current Equivalent Model" cell.

Progress LoadMaster release and support pattern

Of the 77 release lines tracked, 37 are past end of life and 40 are still within support; 27 are marked end of life without a published date. No end-of-life date is currently published for the 40 supported lines.

Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.

What does Progress LoadMaster end of life mean for your organization?

When a version of Progress LoadMaster reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.

The CVE blind spot: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no vendor patch is coming. This is one of the most dangerous gaps in enterprise security posture.

Organizations running EOL Progress LoadMaster should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.

Your options when Progress LoadMaster reaches end of life

There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.

How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.

Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.

Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.

Extended Support Options

If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Progress LoadMaster versions. This is a bridge, not a permanent solution — plan your migration in parallel.

Related Products